Devices and Method for Manipulating User Interfaces with Stylus and Non-Stylus Contacts

ABSTRACT

An electronic device with a touch-sensitive display and one or more sensors to detect signals from a stylus associated with the device displays a user interface in a viewing mode, the user interface including a content region and a first control region. While displaying the user interface in the viewing mode, the device detects an input by a first contact on the touch-sensitive display; and, in response to detecting the input: when the first contact is a stylus contact in the content region, the device displays, in the content region, a mark drawn in accordance with movement of the first contact in the input. If the first contact is a non-stylus contact in the content region, the device performs a navigation operation in the content region in accordance with movement of the first contact without displaying the mark that corresponds to the first contact in the content region.

RELATED APPLICATIONS

This application is a continuation of Ser. No. 15/620,737, filed Jun.12, 2017, which claims priority to U.S. Provisional Application Ser. No.62/349,063, filed Jun. 12, 2016, entitled “Devices and Methods forManipulating User Interfaces with Stylus and Non-Stylus Contacts,” eachof which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

This relates generally to electronic devices with touch-sensitivesurfaces, including but not limited to electronic devices withtouch-sensitive surfaces that manipulate user interfaces with stylus andnon-stylus contacts.

BACKGROUND

The use of touch-sensitive surfaces as input devices for computers andother electronic computing devices has increased significantly in recentyears. Exemplary touch-sensitive surfaces include touchpads andtouch-screen displays. Such surfaces are widely used to manipulate userinterface objects on a display.

User interfaces can be manipulated with either finger or stylus inputs.Finger inputs are more common than stylus inputs, in part becauseconventional methods that use styluses are cumbersome and inefficient.

SUMMARY

Accordingly, disclosed herein are electronic devices with faster, moreefficient methods for manipulating user interfaces in applications(e.g., an application that views and edits images and Portable DocumentFiles (PDFs), such as Preview from Apple Inc. of Cupertino, Calif.) withstylus and non-stylus contacts. Such methods optionally complement orreplace conventional methods for manipulating user interfaces withstylus and non-stylus contacts. Such methods reduce the number, extent,and/or nature of the inputs from a user and produce a more efficienthuman-machine interface. For battery-operated devices, such methodsconserve power and increase the time between battery charges.

The above deficiencies and other problems associated with userinterfaces for electronic devices with touch-sensitive surfaces arereduced or eliminated by the disclosed devices. In some embodiments, thedevice is a desktop computer. In some embodiments, the device isportable (e.g., a notebook computer, tablet computer, or handhelddevice). In some embodiments, the device has a touchpad. In someembodiments, the device has a touch-sensitive display (also known as a“touch screen” or “touch-screen display”). In some embodiments, thedevice has a graphical user interface (GUI), one or more processors,memory and one or more modules, programs or sets of instructions storedin the memory for performing multiple functions. In some embodiments,the user interacts with the GUI primarily through stylus and/or fingercontacts and gestures on the touch-sensitive surface. In someembodiments, the functions optionally include image editing, drawing,presenting, word processing, website creating, disk authoring,spreadsheet making, game playing, telephoning, video conferencing,e-mailing, instant messaging, workout support, digital photographing,digital videoing, web browsing, digital music playing, and/or digitalvideo playing. Executable instructions for performing these functionsare, optionally, included in a non-transitory computer readable storagemedium or other computer program product configured for execution by oneor more processors. Executable instructions for performing thesefunctions are, optionally, included in a transitory computer readablemedium or other computer program product configured for execution by oneor more processors.

In accordance with some embodiments, a method is performed at anelectronic device with a touch-sensitive display, the device includingone or more sensors to detect signals from a stylus associated with thedevice. The method includes: displaying a user interface in a viewingmode on the touch-sensitive display, the user interface including acontent region and a first control region; while displaying the userinterface in the viewing mode, detecting an input by a first contact onthe touch-sensitive display; and, in response to detecting the input: inaccordance with a determination that the first contact is a styluscontact in the content region: changing from the viewing mode to anediting mode, distinct from the viewing mode, that is configured toenable drawing on the content region in the user interface; anddisplaying, in the content region, a mark drawn in accordance withmovement of the first contact in the input; in accordance with adetermination that the first contact is a non-stylus contact in thecontent region: remaining in the viewing mode; and performing anavigation operation in the content region in accordance with movementof the first contact in the input without displaying the mark thatcorresponds to the first contact in the content region; in accordancewith a determination that the first contact is a stylus contact in thefirst control region, performing a control operation; and in accordancewith a determination that the first contact is a non-stylus contact inthe first control region, performing the control operation.

In accordance with some embodiments, an electronic device includes atouch-sensitive display unit configured to display a user interface andreceive user contacts (including stylus contacts and non-styluscontacts), one or more sensor units configured to detect signals from astylus associated with the device; and a processing unit coupled withthe touch-sensitive display unit and the one or more sensor units. Theprocessing unit is configured to: enable display of a user interface ina viewing mode on the touch-sensitive display unit, the user interfaceincluding a content region and a first control region; while enablingdisplaying of the user interface in the viewing mode, detect an input bya first contact on the touch-sensitive display unit; and, in response todetecting the input: in accordance with a determination that the firstcontact is a stylus contact in the content region: change from theviewing mode to an editing mode, distinct from the viewing mode, that isconfigured to enable drawing on the content region in the userinterface; and enable display of, in the content region, a mark drawn inaccordance with movement of the first contact in the input; inaccordance with a determination that the first contact is a non-styluscontact in the content region: remain in the viewing mode; and perform anavigation operation in the content region in accordance with movementof the first contact in the input without enabling display of the markthat corresponds to the first contact in the content region; inaccordance with a determination that the first contact is a styluscontact in the first control region, perform a control operation; and inaccordance with a determination that the first contact is a non-styluscontact in the first control region, perform the control operation.

In accordance with some embodiments, an electronic device includes atouch-sensitive display, optionally one or more sensors to detectsignals from a stylus associated with the device, one or moreprocessors, memory, and one or more programs; the one or more programsare stored in the memory and configured to be executed by the one ormore processors and the one or more programs include instructions forperforming or causing performance of the operations of any of themethods described herein. In accordance with some embodiments, acomputer readable storage medium has stored therein instructions whichwhen executed by an electronic device with a touch-sensitive display andoptionally, one or more sensors to detect signals from a stylusassociated with the device, cause the device to perform or causeperformance of the operations of any of the methods described herein. Inaccordance with some embodiments, a graphical user interface on anelectronic device with a touch-sensitive display and optionally, one ormore sensors to detect signals from a stylus associated with the device,a memory, and one or more processors to execute one or more programsstored in the memory includes one or more of the elements displayed inany of the methods described herein, which are updated in response toinputs, as described in any of the methods described herein. Inaccordance with some embodiments, an electronic device includes: atouch-sensitive display, and optionally one or more sensors to detectsignals from a stylus associated with the device; and means forperforming or causing performance of the operations of any of themethods described herein. In accordance with some embodiments, aninformation processing apparatus, for use in an electronic device with atouch-sensitive display, and optionally one or more sensors to detectsignals from a stylus associated with the device, includes means forperforming or causing performance of the operations of any of themethods described herein.

Thus, electronic devices with displays, touch-sensitive surfaces andoptionally one or more sensors to detect signals from a stylusassociated with the device are provided with faster, more efficientmethods for manipulating user interfaces with stylus and non-styluscontacts, thereby increasing the effectiveness, efficiency, and usersatisfaction with such devices. Such methods may complement or replaceconventional methods for manipulating user interfaces with stylus andnon-stylus contacts.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4 is a block diagram of an exemplary electronic stylus inaccordance with some embodiments.

FIGS. 5A-5B illustrate a positional state of a stylus relative to atouch-sensitive surface in accordance with some embodiments

FIG. 6A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 6B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIGS. 7A-7R illustrate exemplary user interfaces for viewing and editingdocuments with stylus and finger inputs in accordance with someembodiments.

FIGS. 8A-8D are flow diagrams illustrating a method of viewing andediting documents with stylus and finger inputs in accordance with someembodiments.

FIG. 9 is a functional block diagram of an electronic device inaccordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

Many electronic devices have an application that views and edits imagesand Portable Document Files (PDFs). Some of these applications allow auser to annotate a PDF document (e.g., with marks, highlighting, notes,etc.) and also allow the user to navigate within the document (e.g.,scrolling up and/or down in the document). However, existing methods forannotating and navigating in PDF documents are slow and inefficient. Forexample, the user may need to activate a drawing affordance before beingable to annotate a document. Further, the user may need to activate aviewing affordance (or alternatively, to deactivate the drawingaffordance) before being able to navigate within the document. Further,in conventional methods, stylus contacts and non-stylus contacts areused interchangeably and are not able to serve different roles. Theembodiments below address these problems by providing a method thatallows simultaneous annotation with a stylus contact and navigation witha non-stylus contact (e.g., a finger) without having to activate amode-change affordance.

Below, FIGS. 1A-1B, 2, 3, 4, 5A-5B, and 6A-6B provide a description ofexemplary devices. FIGS. 7A-7R illustrate exemplary user interfaces forviewing and editing documents with stylus and finger inputs. FIGS. 8A-8Dare flow diagrams illustrating a method of viewing and editing documentswith stylus and finger inputs. The user interfaces in FIGS. 7A-7R areused to illustrate the processes in FIGS. 8A-8D.

Exemplary Devices

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact, unless the contextclearly indicates otherwise.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch-screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch-screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display system112 is sometimes called a “touch screen” for convenience, and issometimes simply called a touch-sensitive display. Device 100 includesmemory 102 (which optionally includes one or more computer readablestorage mediums), memory controller 120, one or more processing units(CPUs) 122, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input or control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more intensity sensors 165 for detectingintensity of contacts on device 100 (e.g., a touch-sensitive surfacesuch as touch-sensitive display system 112 of device 100). Device 100optionally includes one or more tactile output generators 163 forgenerating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 102 by othercomponents of device 100, such as CPU(s) 122 and the peripheralsinterface 118, is, optionally, controlled by memory controller 120.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU(s) 122 and memory 102. The one or moreprocessors 122 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data.

In some embodiments, peripherals interface 118, CPU(s) 122, and memorycontroller 120 are, optionally, implemented on a single chip, such aschip 104. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch-sensitive display system 112 and other input or control devices116, with peripherals interface 118. I/O subsystem 106 optionallyincludes display controller 156, optical sensor controller 158,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input or control devices 116. The other input or controldevices 116 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, joysticks, click wheels,and so forth. In some alternate embodiments, input controller(s) 160are, optionally, coupled with any (or none) of the following: akeyboard, infrared port, USB port, stylus, and/or a pointer device suchas a mouse. The one or more buttons (e.g., 208, FIG. 2) optionallyinclude an up/down button for volume control of speaker 111 and/ormicrophone 113. The one or more buttons optionally include a push button(e.g., 206, FIG. 2).

Touch-sensitive display system 112 provides an input interface and anoutput interface between the device and a user. Display controller 156receives and/or sends electrical signals from/to touch-sensitive displaysystem 112. Touch-sensitive display system 112 displays visual output tothe user. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds touser-interface objects.

Touch-sensitive display system 112 has a touch-sensitive surface, sensoror set of sensors that accepts input from the user based onhaptic/tactile contact. Touch-sensitive display system 112 and displaycontroller 156 (along with any associated modules and/or sets ofinstructions in memory 102) detect contact (and any movement or breakingof the contact) on touch-sensitive display system 112 and converts thedetected contact into interaction with user-interface objects (e.g., oneor more soft keys, icons, web pages or images) that are displayed ontouch-sensitive display system 112. In an exemplary embodiment, a pointof contact between touch-sensitive display system 112 and the usercorresponds to a finger of the user or a stylus.

Touch-sensitive display system 112 optionally uses LCD (liquid crystaldisplay) technology, LPD (light emitting polymer display) technology, orLED (light emitting diode) technology, although other displaytechnologies are used in other embodiments. Touch-sensitive displaysystem 112 and display controller 156 optionally detect contact and anymovement or breaking thereof using any of a plurality of touch sensingtechnologies now known or later developed, including but not limited tocapacitive, resistive, infrared, and surface acoustic wave technologies,as well as other proximity sensor arrays or other elements fordetermining one or more points of contact with touch-sensitive displaysystem 112. In an exemplary embodiment, projected mutual capacitancesensing technology is used, such as that found in the iPhone®, iPodTouch®, and iPad® from Apple Inc. of Cupertino, Calif.

Touch-sensitive display system 112 optionally has a video resolution inexcess of 100 dpi. In some embodiments, the touch screen videoresolution is in excess of 400 dpi (e.g., 500 dpi, 800 dpi, or greater).The user optionally makes contact with touch-sensitive display system112 using any suitable object or appendage, such as a stylus, a finger,and so forth. In some embodiments, the user interface is designed towork with finger-based contacts and gestures, which can be less precisethan stylus-based input due to the larger area of contact of a finger onthe touch screen. In some embodiments, the device translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch-sensitive displaysystem 112 or an extension of the touch-sensitive surface formed by thetouch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled with optical sensor controller158 in I/O subsystem 106. Optical sensor(s) 164 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 164 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 143(also called a camera module), optical sensor(s) 164 optionally capturestill images and/or video. In some embodiments, an optical sensor islocated on the back of device 100, opposite touch-sensitive displaysystem 112 on the front of the device, so that the touch screen isenabled for use as a viewfinder for still and/or video imageacquisition. In some embodiments, another optical sensor is located onthe front of the device so that the user's image is obtained (e.g., forselfies, for videoconferencing while the user views the other videoconference participants on the touch screen, etc.).

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled withintensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor(s) 165 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a touch-sensitive surface). Contactintensity sensor(s) 165 receive contact intensity information (e.g.,pressure information or a proxy for pressure information) from theenvironment. In some embodiments, at least one contact intensity sensoris collocated with, or proximate to, a touch-sensitive surface (e.g.,touch-sensitive display system 112). In some embodiments, at least onecontact intensity sensor is located on the back of device 100, oppositetouch-screen display system 112 which is located on the front of device100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled with peripherals interface118. Alternately, proximity sensor 166 is coupled with input controller160 in I/O subsystem 106. In some embodiments, the proximity sensorturns off and disables touch-sensitive display system 112 when themultifunction device is placed near the user's ear (e.g., when the useris making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 163. FIG. 1A shows a tactile output generator coupled withhaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator(s) 163 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 163 receive tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch-sensitive display system 112, which islocated on the front of device 100.

Device 100 optionally also includes one or more accelerometers 167,gyroscopes 168, and/or magnetometers 169 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning theposition (e.g., attitude) of the device. FIG. 1A shows sensors 167, 168,and 169 coupled with peripherals interface 118. Alternately, sensors167, 168, and 169 are, optionally, coupled with an input controller 160in I/O subsystem 106. In some embodiments, information is displayed onthe touch-screen display in a portrait view or a landscape view based onan analysis of data received from the one or more accelerometers. Device100 optionally includes a GPS (or GLONASS or other global navigationsystem) receiver (not shown) for obtaining information concerning thelocation of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,position module (or set of instructions) 131, graphics module (or set ofinstructions) 132, haptic feedback module (or set of instructions) 133,text input module (or set of instructions) 134, Global PositioningSystem (GPS) module (or set of instructions) 135, and applications (orsets of instructions) 136. Furthermore, in some embodiments, memory 102stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch-sensitive display system112; sensor state, including information obtained from the device'svarious sensors and other input or control devices 116; and locationand/or positional information concerning the device's location and/orattitude.

Operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with the30-pin connector used in some iPhone®, iPod Touch®, and iPad® devicesfrom Apple Inc. of Cupertino, Calif. In some embodiments, the externalport is a Lightning connector that is the same as, or similar to and/orcompatible with the Lightning connector used in some iPhone®, iPodTouch®, and iPad® devices from Apple Inc. of Cupertino, Calif.

Contact/motion module 130 optionally detects contact withtouch-sensitive display system 112 (in conjunction with displaycontroller 156) and other touch-sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 130 includes softwarecomponents for performing various operations related to detection ofcontact (e.g., by a finger or by a stylus), such as determining ifcontact has occurred (e.g., detecting a finger-down event), determiningan intensity of the contact (e.g., the force or pressure of the contactor a substitute for the force or pressure of the contact), determiningif there is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 130receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one finger contactsor stylus contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts and/or stylus contacts). In someembodiments, contact/motion module 130 and display controller 156 detectcontact on a touchpad.

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (lift off) event. Similarly, tap,swipe, drag, and other gestures are optionally detected for a stylus bydetecting a particular contact pattern for the stylus.

Position module 131, in conjunction with accelerometers 167, gyroscopes168, and/or magnetometers 169, optionally detects positional informationconcerning the device, such as the device's attitude (roll, pitch,and/or yaw) in a particular frame of reference. Position module 130includes software components for performing various operations relatedto detecting the position of the device and detecting changes to theposition of the device. In some embodiments, position module 131 usesinformation received from a stylus being used with the device to detectpositional information concerning the stylus, such as detecting thepositional state of the stylus relative to the device and detectingchanges to the positional state of the stylus.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch-sensitive display system 112or other display, including components for changing the visual impact(e.g., brightness, transparency, saturation, contrast or other visualproperty) of graphics that are displayed. As used herein, the term“graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 163 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing, to camera 143 as picture/video metadata,and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   contacts module 137 (sometimes called an address book or contact        list);    -   telephone module 138;    -   video conferencing module 139;    -   e-mail client module 140;    -   instant messaging (IM) module 141;    -   workout support module 142;    -   camera module 143 for still and/or video images;    -   image management module 144;    -   browser module 147;    -   calendar module 148;    -   widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   widget creator module 150 for making user-created widgets 149-6;    -   search module 151;    -   video and music player module 152, which is, optionally, made up        of a video player module and a music player module;    -   notes module 153;    -   map module 154; and/or    -   video editing module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, contacts module 137 includes executable instructions tomanage an address book or contact list (e.g., stored in applicationinternal state 192 of contacts module 137 in memory 102 or memory 370),including: adding name(s) to the address book; deleting name(s) from theaddress book; associating telephone number(s), e-mail address(es),physical address(es) or other information with a name; associating animage with a name; categorizing and sorting names; providing telephonenumbers and/or e-mail addresses to initiate and/or facilitatecommunications by telephone 138, video conference 139, e-mail 140, or IM141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, contact module 130, graphics module 132, and text input module 134,telephone module 138 includes executable instructions to enter asequence of characters corresponding to a telephone number, access oneor more telephone numbers in address book 137, modify a telephone numberthat has been entered, dial a respective telephone number, conduct aconversation and disconnect or hang up when the conversation iscompleted. As noted above, the wireless communication optionally usesany of a plurality of communications standards, protocols andtechnologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch-sensitive display system 112, display controller156, optical sensor(s) 164, optical sensor controller 158, contactmodule 130, graphics module 132, text input module 134, contact list137, and telephone module 138, videoconferencing module 139 includesexecutable instructions to initiate, conduct, and terminate a videoconference between a user and one or more other participants inaccordance with user instructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,and text input module 134, the instant messaging module 141 includesexecutable instructions to enter a sequence of characters correspondingto an instant message, to modify previously entered characters, totransmit a respective instant message (for example, using a ShortMessage Service (SMS) or Multimedia Message Service (MMS) protocol fortelephony-based instant messages or using XMPP, SIMPLE, Apple PushNotification Service (APNs) or IMPS for Internet-based instantmessages), to receive instant messages and to view received instantmessages. In some embodiments, transmitted and/or received instantmessages optionally include graphics, photos, audio files, video filesand/or other attachments as are supported in a MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, APNs,or IMPS).

In conjunction with RF circuitry 108, touch-sensitive display system112, display controller 156, contact module 130, graphics module 132,text input module 134, GPS module 135, map module 154, and music playermodule 152, workout support module 142 includes executable instructionsto create workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (in sports devices and smartwatches); receive workout sensor data; calibrate sensors used to monitora workout; select and play music for a workout; and display, store andtransmit workout data.

In conjunction with touch-sensitive display system 112, displaycontroller 156, optical sensor(s) 164, optical sensor controller 158,contact module 130, graphics module 132, and image management module144, camera module 143 includes executable instructions to capture stillimages or video (including a video stream) and store them into memory102, modify characteristics of a still image or video, and/or delete astill image or video from memory 102.

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, text inputmodule 134, and camera module 143, image management module 144 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, and text input module 134, browser module 147 includes executableinstructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, e-mail client module 140, and browser module147, calendar module 148 includes executable instructions to create,display, modify, and store calendars and data associated with calendars(e.g., calendar entries, to do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, widget modules 149are mini-applications that are, optionally, downloaded and used by auser (e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, and browser module 147, the widget creatormodule 150 includes executable instructions to create widgets (e.g.,turning a user-specified portion of a web page into a widget).

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, and text inputmodule 134, search module 151 includes executable instructions to searchfor text, music, sound, image, video, and/or other files in memory 102that match one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, RF circuitry 108, and browser module 147, video andmusic player module 152 includes executable instructions that allow theuser to download and play back recorded music and other sound filesstored in one or more file formats, such as MP3 or AAC files, andexecutable instructions to display, present or otherwise play backvideos (e.g., on touch-sensitive display system 112, or on an externaldisplay connected wirelessly or via external port 124). In someembodiments, device 100 optionally includes the functionality of an MP3player, such as an iPod® (trademark of Apple Inc.).

In conjunction with touch-sensitive display system 112, displaycontroller 156, contact module 130, graphics module 132, and text inputmodule 134, notes module 153 includes executable instructions to createand manage notes, to do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch-sensitive display system112, display system controller 156, contact module 130, graphics module132, text input module 134, GPS module 135, and browser module 147, mapmodule 154 includes executable instructions to receive, display, modify,and store maps and data associated with maps (e.g., driving directions;data on stores and other points of interest at or near a particularlocation; and other location-based data) in accordance with userinstructions.

In conjunction with touch-sensitive display system 112, display systemcontroller 156, contact module 130, graphics module 132, audio circuitry110, speaker 111, text input module 134, video editing module 155includes executable instructions that allow the user to edit movies andother videos (e.g., iMovie® from Apple Inc. of Cupertino, Calif.).

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 102 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 102 optionally stores additionalmodules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 136, 137-155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay system 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display system 112, as part of amulti-touch gesture). Peripherals interface 118 transmits information itreceives from I/O subsystem 106 or a sensor, such as proximity sensor166, accelerometer(s) 167, gyroscope(s) 168, magnetometer(s) 169, and/ormicrophone 113 (through audio circuitry 110). Information thatperipherals interface 118 receives from I/O subsystem 106 includesinformation from touch-sensitive display system 112 or a touch-sensitivesurface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripheral interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more views,when touch-sensitive display system 112 displays more than one view.Views are made up of controls and other elements that a user can see onthe display.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver module182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177 or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 includes one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170, and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event 187 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay system 112, and lift-off of the touch (touch end). In someembodiments, the event also includes information for one or moreassociated event handlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display system 112, when a touch is detected ontouch-sensitive display system 112, event comparator 184 performs a hittest to determine which of the three user-interface objects isassociated with the touch (sub-event). If each displayed object isassociated with a respective event handler 190, the event comparatoruses the result of the hit test to determine which event handler 190should be activated. For example, event comparator 184 selects an eventhandler associated with the sub-event and the object triggering the hittest.

In some embodiments, the definition for a respective event 187 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module 145. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen (e.g., touch-sensitive display system 112, FIG. 1A) in accordancewith some embodiments. The touch screen optionally displays one or moregraphics within user interface (UI) 200. In this embodiment, as well asothers described below, a user is enabled to select one or more of thegraphics by making a gesture on the graphics, for example, with one ormore fingers 202 (not drawn to scale in the figure) or one or morestyluses 203 (not drawn to scale in the figure). In some embodiments,selection of one or more graphics occurs when the user breaks contactwith the one or more graphics. In some embodiments, the gestureoptionally includes one or more taps, one or more swipes (from left toright, right to left, upward and/or downward) and/or a rolling of afinger (from right to left, left to right, upward and/or downward) thathas made contact with device 100. In some implementations orcircumstances, inadvertent contact with a graphic does not select thegraphic. For example, a swipe gesture that sweeps over an applicationicon optionally does not select the corresponding application when thegesture corresponding to selection is a tap.

Device 100 optionally also includes one or more physical buttons, suchas “home” or menu button 204. As described previously, menu button 204is, optionally, used to navigate to any application 136 in a set ofapplications that are, optionally executed on device 100. Alternatively,in some embodiments, the menu button is implemented as a soft key in aGUI displayed on the touch-screen display.

In some embodiments, device 100 includes the touch-screen display, menubutton 204, push button 206 for powering the device on/off and lockingthe device, volume adjustment button(s) 208, Subscriber Identity Module(SIM) card slot 210, head set jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In some embodiments, device 100 also accepts verbalinput for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch-sensitive display system 112 and/or one or more tactile outputgenerators 163 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPU's) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch-screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 163 described above with reference to FIG. 1A), sensors 359(e.g., touch-sensitive, optical, contact intensity, proximity,acceleration, attitude, and/or magnetic sensors similar to sensors 112,164, 165, 166, 167, 168, and 169 described above with reference to FIG.1A). Memory 370 includes high-speed random access memory, such as DRAM,SRAM, DDR RAM or other random access solid state memory devices; andoptionally includes non-volatile memory, such as one or more magneticdisk storage devices, optical disk storage devices, flash memorydevices, or other non-volatile solid state storage devices. Memory 370optionally includes one or more storage devices remotely located fromCPU(s) 310. In some embodiments, memory 370 stores programs, modules,and data structures analogous to the programs, modules, and datastructures stored in memory 102 of portable multifunction device 100(FIG. 1A), or a subset thereof. Furthermore, memory 370 optionallystores additional programs, modules, and data structures not present inmemory 102 of portable multifunction device 100. For example, memory 370of device 300 optionally stores drawing module 380, presentation module382, word processing module 384, website creation module 386, diskauthoring module 388, and/or spreadsheet module 390, while memory 102 ofportable multifunction device 100 (FIG. 1A) optionally does not storethese modules.

Each of the above identified elements in FIG. 3 are, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove identified modules corresponds to a set of instructions forperforming a function described above. The above identified modules orprograms (i.e., sets of instructions) need not be implemented asseparate software programs, procedures or modules, and thus varioussubsets of these modules are, optionally, combined or otherwisere-arranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

FIG. 4 is a block diagram of an exemplary electronic stylus 203 inaccordance with some embodiments. Electronic stylus 203 is sometimessimply called a stylus. Stylus 203 includes memory 402 (which optionallyincludes one or more computer readable storage mediums), memorycontroller 422, one or more processing units (CPUs) 420, peripheralsinterface 418, RF circuitry 408, input/output (I/O) subsystem 406, andother input or control devices 416. Stylus 203 optionally includesexternal port 424 and one or more optical sensors 464. Stylus 203optionally includes one or more intensity sensors 465 for detectingintensity of contacts of stylus 203 on device 100 (e.g., when stylus 203is used with a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100) or on other surfaces (e.g., a desk surface).Stylus 203 optionally includes one or more tactile output generators 463for generating tactile outputs on stylus 203. These componentsoptionally communicate over one or more communication buses or signallines 403.

In some embodiments, the term “tactile output,” discussed above, refersto physical displacement of an accessory (e.g., stylus 203) of a device(e.g., device 100) relative to a previous position of the accessory,physical displacement of a component of an accessory relative to anothercomponent of the accessory, or displacement of the component relative toa center of mass of the accessory that will be detected by a user withthe user's sense of touch. For example, in situations where theaccessory or the component of the accessory is in contact with a surfaceof a user that is sensitive to touch (e.g., a finger, palm, or otherpart of a user's hand), the tactile output generated by the physicaldisplacement will be interpreted by the user as a tactile sensationcorresponding to a perceived change in physical characteristics of theaccessory or the component of the accessory. For example, movement of acomponent (e.g., the housing of stylus 203) is, optionally, interpretedby the user as a “click” of a physical actuator button. In some cases, auser will feel a tactile sensation such as a “click” even when there isno movement of a physical actuator button associated with the stylusthat is physically pressed (e.g., displaced) by the user's movements.While such interpretations of touch by a user will be subject to theindividualized sensory perceptions of the user, there are many sensoryperceptions of touch that are common to a large majority of users. Thus,when a tactile output is described as corresponding to a particularsensory perception of a user (e.g., a “click,”), unless otherwisestated, the generated tactile output corresponds to physicaldisplacement of the device or a component thereof that will generate thedescribed sensory perception for a typical (or average) user.

It should be appreciated that stylus 203 is only one example of anelectronic stylus, and that stylus 203 optionally has more or fewercomponents than shown, optionally combines two or more components, oroptionally has a different configuration or arrangement of thecomponents. The various components shown in FIG. 4 are implemented inhardware, software, firmware, or a combination thereof, including one ormore signal processing and/or application specific integrated circuits.

Memory 402 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or more flashmemory devices, or other non-volatile solid-state memory devices. Accessto memory 402 by other components of stylus 203, such as CPU(s) 420 andthe peripherals interface 418, is, optionally, controlled by memorycontroller 422.

Peripherals interface 418 can be used to couple input and outputperipherals of the stylus to CPU(s) 420 and memory 402. The one or moreprocessors 420 run or execute various software programs and/or sets ofinstructions stored in memory 402 to perform various functions forstylus 203 and to process data.

In some embodiments, peripherals interface 418, CPU(s) 420, and memorycontroller 422 are, optionally, implemented on a single chip, such aschip 404. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 408 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 408 converts electricalsignals to/from electromagnetic signals and communicates with device 100or 300, communications networks, and/or other communications devices viathe electromagnetic signals. RF circuitry 408 optionally includeswell-known circuitry for performing these functions, including but notlimited to an antenna system, an RF transceiver, one or more amplifiers,a tuner, one or more oscillators, a digital signal processor, a CODECchipset, a subscriber identity module (SIM) card, memory, and so forth.RF circuitry 408 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSDPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g and/or IEEE802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol fore-mail (e.g., Internet message access protocol (IMAP) and/or post officeprotocol (POP)), instant messaging (e.g., extensible messaging andpresence protocol (XMPP), Session Initiation Protocol for InstantMessaging and Presence Leveraging Extensions (SIMPLE), Instant Messagingand Presence Service (IMPS)), and/or Short Message Service (SMS), or anyother suitable communication protocol, including communication protocolsnot yet developed as of the filing date of this document.

I/O subsystem 406 couples input/output peripherals on stylus 203, suchas other input or control devices 416, with peripherals interface 418.I/O subsystem 406 optionally includes optical sensor controller 458,intensity sensor controller 459, haptic feedback controller 461, and oneor more input controllers 460 for other input or control devices. Theone or more input controllers 460 receive/send electrical signalsfrom/to other input or control devices 416. The other input or controldevices 416 optionally include physical buttons (e.g., push buttons,rocker buttons, etc.), dials, slider switches, click wheels, and soforth. In some alternate embodiments, input controller(s) 460 are,optionally, coupled with any (or none) of the following: an infraredport and/or a USB port.

Stylus 203 also includes power system 462 for powering the variouscomponents. Power system 462 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices and/or portableaccessories.

Stylus 203 optionally also includes one or more optical sensors 464.FIG. 4 shows an optical sensor coupled with optical sensor controller458 in I/O subsystem 406. Optical sensor(s) 464 optionally includecharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor(s) 464 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image.

Stylus 203 optionally also includes one or more contact intensitysensors 465. FIG. 4 shows a contact intensity sensor coupled withintensity sensor controller 459 in I/O subsystem 406. Contact intensitysensor(s) 465 optionally include one or more piezoresistive straingauges, capacitive force sensors, electric force sensors, piezoelectricforce sensors, optical force sensors, capacitive touch-sensitivesurfaces, or other intensity sensors (e.g., sensors used to measure theforce (or pressure) of a contact on a surface). Contact intensitysensor(s) 465 receive contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a tip of stylus 203.

Stylus 203 optionally also includes one or more proximity sensors 466.FIG. 4 shows proximity sensor 466 coupled with peripherals interface418. Alternately, proximity sensor 466 is coupled with input controller460 in I/O subsystem 406. In some embodiments, the proximity sensordetermines proximity of stylus 203 to an electronic device (e.g., device100).

Stylus 203 optionally also includes one or more tactile outputgenerators 463. FIG. 4 shows a tactile output generator coupled withhaptic feedback controller 461 in I/O subsystem 406. Tactile outputgenerator(s) 463 optionally include one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Tactile output generator(s) 463 receive tactile feedbackgeneration instructions from haptic feedback module 433 and generatestactile outputs on stylus 203 that are capable of being sensed by a userof stylus 203. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a length (e.g., a body ora housing) of stylus 203 and, optionally, generates a tactile output bymoving stylus 203 vertically (e.g., in a direction parallel to thelength of stylus 203) or laterally (e.g., in a direction normal to thelength of stylus 203).

Stylus 203 optionally also includes one or more accelerometers 467,gyroscopes 468, and/or magnetometers 469 (e.g., as part of an inertialmeasurement unit (IMU)) for obtaining information concerning thelocation and positional state of stylus 203. FIG. 4 shows sensors 467,468, and 469 coupled with peripherals interface 418. Alternately,sensors 467, 468, and 469 are, optionally, coupled with an inputcontroller 460 in I/O subsystem 406. Stylus 203 optionally includes aGPS (or GLONASS or other global navigation system) receiver (not shown)for obtaining information concerning the location of stylus 203.

In some embodiments, the software components stored in memory 402include operating system 426, communication module (or set ofinstructions) 428, contact/motion module (or set of instructions) 430,position module (or set of instructions) 431, and Global PositioningSystem (GPS) module (or set of instructions) 435. Furthermore, in someembodiments, memory 402 stores device/global internal state 457, asshown in FIG. 4. Device/global internal state 457 includes one or moreof: sensor state, including information obtained from the stylus'svarious sensors and other input or control devices 416; positionalstate, including information regarding the stylus's position (e.g.,position, orientation, tilt, roll and/or distance, as shown in FIGS. 5Aand 5B) relative to a device (e.g., device 100); and locationinformation concerning the stylus's location (e.g., determined by GPSmodule 435).

Operating system 426 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, power management, etc.)and facilitates communication between various hardware and softwarecomponents.

Communication module 428 optionally facilitates communication with otherdevices over one or more external ports 424 and also includes varioussoftware components for handling data received by RF circuitry 408and/or external port 424. External port 424 (e.g., Universal Serial Bus(USB), FIREWIRE, etc.) is adapted for coupling directly to other devicesor indirectly over a network (e.g., the Internet, wireless LAN, etc.).In some embodiments, the external port is a Lightning connector that isthe same as, or similar to and/or compatible with the Lightningconnector used in some iPhone®, iPod Touch®, and iPad® devices fromApple Inc. of Cupertino, Calif.

Contact/motion module 430 optionally detects contact with stylus 203 andother touch-sensitive devices of stylus 203 (e.g., buttons or othertouch-sensitive components of stylus 203). Contact/motion module 430includes software components for performing various operations relatedto detection of contact (e.g., detection of a tip of the stylus with atouch-sensitive display, such as touch screen 112 of device 100, or withanother surface, such as a desk surface), such as determining if contacthas occurred (e.g., detecting a touch-down event), determining anintensity of the contact (e.g., the force or pressure of the contact ora substitute for the force or pressure of the contact), determining ifthere is movement of the contact and tracking the movement (e.g., acrosstouch screen 112 of device 100), and determining if the contact hasceased (e.g., detecting a lift-off event or a break in contact). In someembodiments, contact/motion module 430 receives contact data from I/Osubsystem 406. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. As noted above, in some embodiments, one or more of theseoperations related to detection of contact are performed by the deviceusing contact/motion module 130 (in addition to or in place of thestylus using contact/motion module 430).

Contact/motion module 430 optionally detects a gesture input by stylus203. Different gestures with stylus 203 have different contact patterns(e.g., different motions, timings, and/or intensities of detectedcontacts). Thus, a gesture is, optionally, detected by detecting aparticular contact pattern. For example, detecting a single tap gestureincludes detecting a touch-down event followed by detecting a lift-offevent at the same position (or substantially the same position) as thetouch-down event (e.g., at the position of an icon). As another example,detecting a swipe gesture includes detecting a touch-down event followedby detecting one or more stylus-dragging events, and subsequentlyfollowed by detecting a lift-off event. As noted above, in someembodiments, gesture detection is performed by the device usingcontact/motion module 130 (in addition to or in place of the stylususing contact/motion module 430).

Position module 431, in conjunction with accelerometers 467, gyroscopes468, and/or magnetometers 469, optionally detects positional informationconcerning the stylus, such as the stylus's attitude (roll, pitch,and/or yaw) in a particular frame of reference. Position module 431, inconjunction with accelerometers 467, gyroscopes 468, and/ormagnetometers 469, optionally detects stylus movement gestures, such asflicks, taps, and rolls of the stylus. Position module 431 includessoftware components for performing various operations related todetecting the position of the stylus and detecting changes to theposition of the stylus in a particular frame of reference. In someembodiments, position module 431 detects the positional state of thestylus relative to the device and detects changes to the positionalstate of the stylus relative to the device. As noted above, in someembodiments, device 100 or 300 determines the positional state of thestylus relative to the device and changes to the positional state of thestylus using position module 131 (in addition to or in place of thestylus using position module 431).

Haptic feedback module 433 includes various software components forgenerating instructions used by tactile output generator(s) 463 toproduce tactile outputs at one or more locations on stylus 203 inresponse to user interactions with stylus 203.

GPS module 435 determines the location of the stylus and provides thisinformation for use in various applications (e.g., to applications thatprovide location-based services such as an application to find missingdevices and/or accessories).

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 402 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 402 optionally stores additionalmodules and data structures not described above.

FIGS. 5A-5B illustrate a positional state of stylus 203 relative to atouch-sensitive surface (e.g., touch screen 112 of device 100) inaccordance with some embodiments. In some embodiments, the positionalstate of stylus 203 corresponds to (or indicates): a position of aprojection of a tip (or other representative portion) of the stylus onthe touch-sensitive surface (e.g., (x,y) position 504, FIG. 5A), anorientation of the stylus relative to the touch-sensitive surface (e.g.,orientation 506, FIG. 5A), a tilt of the stylus relative to thetouch-sensitive surface (e.g., tilt 512, FIG. 5B), and/or a distance ofthe stylus relative to the touch-sensitive surface (e.g., distance 514,FIG. 5B). In some embodiments, the positional state of stylus 203corresponds to (or indicates) a pitch, yaw, and/or roll of the stylus(e.g., an attitude of the stylus relative to a particular frame ofreference, such as a touch-sensitive surface (e.g., touch screen 112) orthe ground). In some embodiments, the positional state includes a set ofpositional parameters (e.g., one or more positional parameters). In someembodiments, the positional state is detected in accordance with one ormore measurements from stylus 203 that are sent to an electronic device(e.g., device 100). For example, the stylus measures the tilt (e.g.,tilt 512, FIG. 5B) and/or the orientation (e.g., orientation 506, FIG.5A) of the stylus and sends the measurement to device 100. In someembodiments, the positional state is detected in accordance with rawoutput, from one or more electrodes in the stylus, that is sensed by atouch-sensitive surface (e.g., touch screen 112 of device 100) insteadof, or in combination with positional state detected in accordance withone or more measurements from stylus 203. For example, thetouch-sensitive surface receives raw output from one or more electrodesin the stylus and calculates the tilt and/or the orientation of thestylus based on the raw output (optionally, in conjunction withpositional state information provided by the stylus based on sensormeasurements generated by the stylus).

FIG. 5A illustrates stylus 203 relative to a touch-sensitive surface(e.g., touch screen 112 of device 100) from a viewpoint directly abovethe touch-sensitive surface, in accordance with some embodiments. InFIG. 5A, z axis 594 points out of the page (i.e., in a direction normalto a plane of touch screen 112), x axis 590 is parallel to a first edge(e.g., a length) of touch screen 112, y axis 592 is parallel to a secondedge (e.g., a width) of touch screen 112, and y axis 592 isperpendicular to x axis 590.

FIG. 5A illustrates the tip of stylus 203 at (x,y) position 504. In someembodiments, the tip of stylus 203 is a terminus of the stylusconfigured for determining proximity of the stylus to a touch-sensitivesurface (e.g., touch screen 112). In some embodiments, the projection ofthe tip of the stylus on the touch-sensitive surface is an orthogonalprojection. In other words, the projection of the tip of the stylus onthe touch-sensitive surface is a point at the end of a line from thestylus tip to the touch-sensitive surface that is normal to a surface ofthe touch-sensitive surface (e.g., (x,y) position 504 at which the tipof the stylus would touch the touch-sensitive surface if the stylus weremoved directly along a path normal to the touch-sensitive surface). Insome embodiments, the (x,y) position at the lower left corner of touchscreen 112 is position (0,0) (e.g., (0,0) position 502) and other (x,y)positions on touch screen 112 are relative to the lower left corner oftouch screen 112. Alternatively, in some embodiments, the (0,0) positionis located at another position of touch screen 112 (e.g., in the centerof touch screen 112) and other (x,y) positions are relative to the (0,0)position of touch screen 112.

Further, FIG. 5A illustrates stylus 203 with orientation 506. In someembodiments, orientation 506 is an orientation of a projection of stylus203 onto touch screen 112 (e.g., an orthogonal projection of a length ofstylus 203 or a line corresponding to the line between the projection oftwo different points of stylus 203 onto touch screen 112). In someembodiments, orientation 506 is relative to at least one axis in a planeparallel to touch screen 112. In some embodiments, orientation 506 isrelative to a single axis in a plane parallel to touch screen 112 (e.g.,axis 508, with a clockwise rotation angle from axis 508 ranging from 0degrees to 360 degrees, as shown in FIG. 5A). Alternatively, in someembodiments, orientation 506 is relative to a pair of axes in a planeparallel to touch screen 112 (e.g., x axis 590 and y axis 592, as shownin FIG. 5A, or a pair of axes associated with an application displayedon touch screen 112).

In some embodiments, an indication (e.g., indication 516) is displayedon a touch-sensitive display (e.g., touch screen 112 of device 100). Insome embodiments, indication 516 shows where the stylus will touch (ormark) the touch-sensitive display before the stylus touches thetouch-sensitive display. In some embodiments, indication 516 is aportion of a mark that is being drawn on the touch-sensitive display. Insome embodiments, indication 516 is separate from a mark that is beingdrawn on the touch-sensitive display and corresponds to a virtual “pentip” or other element that indicates where a mark will be drawn on thetouch-sensitive display.

In some embodiments, indication 516 is displayed in accordance with thepositional state of stylus 203. For example, in some circumstances,indication 516 is displaced from (x,y) position 504 (as shown in FIGS.5A and 5B), and in other circumstances, indication 516 is not displacedfrom (x,y) position 504 (e.g., indication 516 is displayed at or near(x,y) position 504 when tilt 512 is zero degrees). In some embodiments,indication 516 is displayed, in accordance with the positional state ofthe stylus, with varying color, size (or radius or area), opacity,and/or other characteristics. In some embodiments, the displayedindication accounts for thickness of a glass layer on thetouch-sensitive display, so as to carry through the indication “onto thepixels” of the touch-sensitive display, rather than displaying theindication “on the glass” that covers the pixels.

FIG. 5B illustrates stylus 203 relative to a touch-sensitive surface(e.g., touch screen 112 of device 100) from a side viewpoint of thetouch-sensitive surface, in accordance with some embodiments. In FIG.5B, z axis 594 points in a direction normal to the plane of touch screen112, x axis 590 is parallel to a first edge (e.g., a length) of touchscreen 112, y axis 592 is parallel to a second edge (e.g., a width) oftouch screen 112, and y axis 592 is perpendicular to x axis 590.

FIG. 5B illustrates stylus 203 with tilt 512. In some embodiments, tilt512 is an angle relative to a normal (e.g., normal 510) to a surface ofthe touch-sensitive surface (also called simply the normal to thetouch-sensitive surface). As shown in FIG. 5B, tilt 512 is zero when thestylus is perpendicular/normal to the touch-sensitive surface (e.g.,when stylus 203 is parallel to normal 510) and the tilt increases as thestylus is tilted closer to being parallel to the touch-sensitivesurface.

Further, FIG. 5B illustrates distance 514 of stylus 203 relative to thetouch-sensitive surface. In some embodiments, distance 514 is thedistance from the tip of stylus 203 to the touch-sensitive surface, in adirection normal to the touch-sensitive surface. For example, in FIG.5B, distance 514 is the distance from the tip of stylus 203 to (x,y)position 504.

Although the terms, “x axis,” “y axis,” and “z axis,” are used herein toillustrate certain directions in particular figures, it will beunderstood that these terms do not refer to absolute directions. Inother words, an “x axis” could be any respective axis, and a “y axis”could be a particular axis that is distinct from the x axis. Typically,the x axis is perpendicular to the y axis. Similarly, a “z axis” isdistinct from the “x axis” and the “y axis,” and is typicallyperpendicular to both the “x axis” and the “y axis.”

Further, FIG. 5B illustrates roll 518, a rotation about the length (longaxis) of stylus 203.

Attention is now directed towards embodiments of user interfaces (“UI”)that are, optionally, implemented on portable multifunction device 100.

FIG. 6A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 600 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 602 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 604;    -   Bluetooth indicator 605;    -   Battery status indicator 606;    -   Tray 608 with icons for frequently used applications, such as:        -   Icon 616 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 614 of the number of missed            calls or voicemail messages;        -   Icon 618 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 610 of the number of unread            e-mails;        -   Icon 620 for browser module 147, labeled “Browser;” and        -   Icon 622 for video and music player module 152, also            referred to as iPod® (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 624 for IM module 141, labeled “Messages;”        -   Icon 626 for calendar module 148, labeled “Calendar;”        -   Icon 628 for image management module 144, labeled “Photos;”        -   Icon 630 for camera module 143, labeled “Camera;”        -   Icon 632 for video editing module 155, labeled “Video            Editing;”        -   Icon 634 for stocks widget 149-2, labeled “Stocks;”        -   Icon 636 for map module 154, labeled “Map;”        -   Icon 638 for weather widget 149-1, labeled “Weather;”        -   Icon 640 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 642 for workout support module 142, labeled “Workout            Support;”        -   Icon 644 for notes module 153, labeled “Notes;” and        -   Icon 646 for a settings application or module, which            provides access to settings for device 100 and its various            applications 136.

It should be noted that the icon labels illustrated in FIG. 6A aremerely exemplary. For example, in some embodiments, icon 622 for videoand music player module 152 is labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 6B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 651 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 650. Device300 also, optionally, includes one or more contact intensity sensors(e.g., one or more of sensors 359) for detecting intensity of contactson touch-sensitive surface 651 and/or one or more tactile outputgenerators 357 for generating tactile outputs for a user of device 300.

FIG. 6B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 651 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 650. Althoughmany of the examples that follow will be given with reference to inputson touch screen display 112 (where the touch sensitive surface and thedisplay are combined), in some embodiments, the device detects inputs ona touch-sensitive surface that is separate from the display, as shown inFIG. 6B. In some embodiments, the touch-sensitive surface (e.g., 651 inFIG. 6B) has a primary axis (e.g., 652 in FIG. 6B) that corresponds to aprimary axis (e.g., 653 in FIG. 6B) on the display (e.g., 650). Inaccordance with these embodiments, the device detects contacts (e.g.,660 and 662 in FIG. 6B) with the touch-sensitive surface 651 atlocations that correspond to respective locations on the display (e.g.,in FIG. 6B, 660 corresponds to 668 and 662 corresponds to 670). In thisway, user inputs (e.g., contacts 660 and 662, and movements thereof)detected by the device on the touch-sensitive surface (e.g., 651 in FIG.6B) are used by the device to manipulate the user interface on thedisplay (e.g., 650 in FIG. 6B) of the multifunction device when thetouch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures, etc.), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse based input or a stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 651 in FIG. 6B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display(e.g., touch-sensitive display system 112 in FIG. 1A or the touch screenin FIG. 6A) that enables direct interaction with user interface elementson the touch-screen display, a detected contact on the touch-screen actsas a “focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact or a styluscontact) on the touch-sensitive surface, or to a substitute (proxy) forthe force or pressure of a contact on the touch-sensitive surface. Theintensity of a contact has a range of values that includes at least fourdistinct values and more typically includes hundreds of distinct values(e.g., at least 256). Intensity of a contact is, optionally, determined(or measured) using various approaches and various sensors orcombinations of sensors. For example, one or more force sensorsunderneath or adjacent to the touch-sensitive surface are, optionally,used to measure force at various points on the touch-sensitive surface.In some implementations, force measurements from multiple force sensorsare combined (e.g., a weighted average or a sum) to determine anestimated force of a contact. Similarly, a pressure-sensitive tip of astylus is, optionally, used to determine a pressure of the stylus on thetouch-sensitive surface. Alternatively, the size of the contact areadetected on the touch-sensitive surface and/or changes thereto, thecapacitance of the touch-sensitive surface proximate to the contactand/or changes thereto, and/or the resistance of the touch-sensitivesurface proximate to the contact and/or changes thereto are, optionally,used as a substitute for the force or pressure of the contact on thetouch-sensitive surface. In some implementations, the substitutemeasurements for contact force or pressure are used directly todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is described in units corresponding to thesubstitute measurements). In some implementations, the substitutemeasurements for contact force or pressure are converted to an estimatedforce or pressure and the estimated force or pressure is used todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is a pressure threshold measured in units ofpressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be readily accessible by the user on a reduced-size devicewith limited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

In some embodiments, contact/motion module 130 and/or 430 uses a set ofone or more intensity thresholds to determine whether an operation hasbeen performed by a user (e.g., to determine whether a user has“clicked” on an icon). In some embodiments, at least a subset of theintensity thresholds are determined in accordance with softwareparameters (e.g., the intensity thresholds are not determined by theactivation thresholds of particular physical actuators and can beadjusted without changing the physical hardware of device 100). Forexample, a mouse “click” threshold of a trackpad or touch-screen displaycan be set to any of a large range of predefined thresholds valueswithout changing the trackpad or touch-screen display hardware.Additionally, in some embodiments, a user of the device is provided withsoftware settings for adjusting one or more of the set of intensitythresholds (e.g., by adjusting individual intensity thresholds and/or byadjusting a plurality of intensity thresholds at once with asystem-level click “intensity” parameter).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second intensity threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more intensity thresholds is used to determine whether or not toperform one or more operations (e.g., whether to perform a respectiveoption or forgo performing the respective operation) rather than beingused to determine whether to perform a first operation or a secondoperation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location (e.g.,a drag gesture), at which point the intensity of the contact increases.In this example, the characteristic intensity of the contact at the endlocation may be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmmay be applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The user interface figures described herein optionally include variousintensity diagrams that show the current intensity of the contact on thetouch-sensitive surface relative to one or more intensity thresholds(e.g., a contact detection intensity threshold IT₀, a light pressintensity threshold IT_(L), a deep press intensity threshold IT_(D)(e.g., that is at least initially higher than I_(L)), and/or one or moreother intensity thresholds (e.g., an intensity threshold I_(H) that islower than I_(L))). This intensity diagram is typically not part of thedisplayed user interface, but is provided to aid in the interpretationof the figures. In some embodiments, the light press intensity thresholdcorresponds to an intensity at which the device will perform operationstypically associated with clicking a button of a physical mouse or atrackpad. In some embodiments, the deep press intensity thresholdcorresponds to an intensity at which the device will perform operationsthat are different from operations typically associated with clicking abutton of a physical mouse or a trackpad. In some embodiments, when acontact is detected with a characteristic intensity below the lightpress intensity threshold (e.g., and above a nominal contact-detectionintensity threshold IT₀ below which the contact is no longer detected),the device will move a focus selector in accordance with movement of thecontact on the touch-sensitive surface without performing an operationassociated with the light press intensity threshold or the deep pressintensity threshold. Generally, unless otherwise stated, these intensitythresholds are consistent between different sets of user interfacefigures.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms in duration (e.g., 40, 100, or 120 ms,depending on the magnitude of the second intensity threshold, with thedelay time increasing as the second intensity threshold increases). Thisdelay time helps to avoid accidental deep press inputs. As anotherexample, for some “deep press” inputs, there is a reduced-sensitivitytime period that occurs after the time at which the first intensitythreshold is met. During the reduced-sensitivity time period, the secondintensity threshold is increased. This temporary increase in the secondintensity threshold also helps to avoid accidental deep press inputs.For other deep press inputs, the response to detection of a deep pressinput does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Exemplary factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold IT_(L) to an intensity betweenthe light press intensity threshold IT_(L) and the deep press intensitythreshold IT_(D) is sometimes referred to as a “light press” input. Anincrease of characteristic intensity of the contact from an intensitybelow the deep press intensity threshold IT_(D) to an intensity abovethe deep press intensity threshold IT_(D) is sometimes referred to as a“deep press” input. An increase of characteristic intensity of thecontact from an intensity below the contact-detection intensitythreshold IT₀ to an intensity between the contact-detection intensitythreshold IT₀ and the light press intensity threshold IT_(L) issometimes referred to as detecting the contact on the touch-surface. Adecrease of characteristic intensity of the contact from an intensityabove the contact-detection intensity threshold IT₀ to an intensitybelow the contact-detection intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments, IT₀ is greaterthan zero. In some illustrations a shaded circle or oval is used torepresent intensity of a contact on the touch-sensitive surface. In someillustrations, a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments, described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., the respective operation is performed on a“down stroke” of the respective press input). In some embodiments, thepress input includes an increase in intensity of the respective contactabove the press-input intensity threshold and a subsequent decrease inintensity of the contact below the press-input intensity threshold, andthe respective operation is performed in response to detecting thesubsequent decrease in intensity of the respective contact below thepress-input threshold (e.g., the respective operation is performed on an“up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., the respective operationis performed on an “up stroke” of the respective press input).Similarly, in some embodiments, the press input is detected only whenthe device detects an increase in intensity of the contact from anintensity at or below the hysteresis intensity threshold to an intensityat or above the press-input intensity threshold and, optionally, asubsequent decrease in intensity of the contact to an intensity at orbelow the hysteresis intensity, and the respective operation isperformed in response to detecting the press input (e.g., the increasein intensity of the contact or the decrease in intensity of the contact,depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting: an increase in intensityof a contact above the press-input intensity threshold, an increase inintensity of a contact from an intensity below the hysteresis intensitythreshold to an intensity above the press-input intensity threshold, adecrease in intensity of the contact below the press-input intensitythreshold, or a decrease in intensity of the contact below thehysteresis intensity threshold corresponding to the press-inputintensity threshold. Additionally, in examples where an operation isdescribed as being performed in response to detecting a decrease inintensity of a contact below the press-input intensity threshold, theoperation is, optionally, performed in response to detecting a decreasein intensity of the contact below a hysteresis intensity thresholdcorresponding to, and lower than, the press-input intensity threshold.As described above, in some embodiment, the triggering of theseresponses also depends on time-based criteria being met (e.g., a delaytime has elapsed between a first intensity threshold being met and asecond intensity threshold being met).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that may be implemented on an electronicdevice, such as portable multifunction device 100 or device 300, with atouch-sensitive display and optionally one or more sensors to detectsignals from a stylus associated with the device.

FIGS. 7A-7R illustrate exemplary user interfaces for viewing and editingdocuments with stylus and finger inputs in accordance with someembodiments. The user interfaces in these figures are used to illustratethe processes described below, including the processes in FIGS. 8A-8D.Although some of the examples which follow will be given with referenceto inputs on a touch-screen display (where the touch-sensitive surfaceand the display are combined, for example on touch screen 112), in someembodiments, the device detects inputs on a touch-sensitive surface 651that is separate from the display 650, as shown in FIG. 6B. For sake ofclarity, FIGS. 7A-7R simply show touch screen 112 of device 100, withoutshowing other details of device 100.

In some embodiments, the device is an electronic device with a separatedisplay (e.g., display 650) and a separate touch-sensitive surface(e.g., touch-sensitive surface 651). In some embodiments, the device isportable multifunction device 100, the display is touch-sensitivedisplay system 112, and the touch-sensitive surface includes tactileoutput generators 163 on the display (FIG. 1A). For convenience ofexplanation, the embodiments described with reference to FIGS. 7A-7R and8A-8D will be discussed with reference to operations performed on adevice with a touch-sensitive display system 112. In such embodiments,the focus selector is, optionally: a respective finger or styluscontact, a representative point corresponding to a finger or styluscontact (e.g., a centroid of a respective contact or a point associatedwith a respective contact), or a centroid of two or more contactsdetected on the touch-sensitive display system 112. However, analogousoperations are, optionally, performed on a device with a display 650 anda separate touch-sensitive surface 651 in response to detecting thecontacts described in FIGS. 7A-7R on (or near) the touch-sensitivesurface 651 while displaying the user interfaces shown in FIGS. 7A-7R onthe display 650.

FIG. 7A illustrates an example of displaying a user interface of anapplication that views and edits images and Portable Document Files(PDFs) (e.g., an application such as the Preview application from AppleInc. of Cupertino, Calif.). User interface 710 is displayed on a display(e.g., touch screen 112) of a device (e.g., device 100) and isresponsive to contacts (e.g., a stylus contact and/or a finger contact)on the display (e.g., touch screen 112). User interface 710 includescontent region 712 and first control region 714. In some embodiments,first control region 714 includes controls for editing the content incontent region 712. In some embodiments, first control region 714includes controls for navigating through the content in content region712. In some embodiments, first control region 714 includes menuaffordance 714-a, deletion affordance 714-b, revert affordance 714-c,edit mode affordance 714-d, and sharing affordance 714-e. In someembodiments, when an input (e.g., a tap input) is detected on menuaffordance 714-a, a menu is displayed for opening a document. In someembodiments, when an input (e.g., a tap input) is detected on deletionaffordance 714-b, the document is deleted. In some embodiments when aninput (e.g., a tap input) is detected on revert affordance 714-c,changes are undone in the document (e.g., the most recent change or allchanges made since opening the document). In some embodiments, when aninput (e.g., a tap input) is detected on edit mode affordance 714-d, asecond control region (e.g., second control region 716, FIG. 7B) isdisplayed. In some embodiments, when an input (e.g., a tap input) isdetected on sharing affordance 714-e, a menu is displayed with optionsfor sharing the document. In FIG. 7A, user interface 710 is displayed ina viewing mode (e.g., a read-only mode or other mode that does notpermit markup or editing of the content).

FIG. 7B illustrates an example of detecting an input by a stylus contact(e.g., contact 718 by stylus 203) on the touch-sensitive display (e.g.,touch screen 112) in the content region (e.g., content region 712). Insome embodiments, in response to detecting an input by a stylus contact(e.g., contact 718 by stylus 203) in content region 712, user interface710 changes from a viewing mode (e.g., in FIG. 7A) to an editing mode(e.g., in FIG. 7B), where the editing mode is distinct from the viewingmode. In some embodiments, the editing mode, as shown in FIG. 7B, isconfigured to enable drawing on content region 712 by a stylus (e.g.,stylus 203). In some embodiments, in response to detecting an input by astylus (e.g., contact 718 by stylus 203) in content region 712, secondcontrol region 716, distinct from first control region 714, isdisplayed. In some embodiments, second control region 716 includes oneor more tools, such as a drawing tool (e.g., draw affordance 716-a) toenable drawing on content region 712 (e.g., where both stylus contactsand non-stylus contacts are enabled to make marks in the contentregion), a zoom tool (e.g., zoom affordance 716-b) to change themagnification of a selected portion of the document, a text tool (e.g.,text affordance 716-c) to type text in a text box, a signature tool(e.g., signature affordance 716-d) to insert a signature into a PDFdocument, a color tool (e.g., color affordance 716-e) to change thecolor of marks drawn in the content region, a line thickness tool (e.g.,thickness affordance 716-f) to change the thickness of the marks drawnin the content region, and a font tool (e.g., font affordance 716-g) tochange the font type, font size, and/or font alignment of text in thedocument. In some embodiments, second control region 716 appears to fadein through an animation of second control region 716 appearing on thetouch-sensitive display (e.g., touch screen 112) beginning at a time ofinitial contact of stylus 203 in content region 712.

FIGS. 7C-7D illustrate an example of detecting an input that includesmovement across the touch-sensitive display (e.g., touch screen 112) bya stylus contact (e.g., contact 718 by stylus 203) in the content region(e.g., content region 712) and displaying a mark (e.g., mark 719) drawnin accordance with movement of the contact in the input.

FIG. 7E illustrates an example of detecting an input by a non-styluscontact (e.g., contact 720 by finger 202) on the touch-sensitive display(e.g., touch screen 112) in the content region (e.g., content region712). In some embodiments, in response to detecting an input by anon-stylus contact (e.g., contact 720 by finger 202) in content region712, user interface remains in viewing mode (e.g., as shown in FIGS. 7Aand 7E) and forgoes changing from viewing mode to an editing mode.

FIGS. 7F-7G illustrate an example of detecting an input that includesmovement across the touch-sensitive display (e.g., touch screen 112) bya non-stylus contact (e.g., contact 720 by finger 202) in the contentregion (e.g., content region 712) and performing a navigation operationin the content region in accordance with movement of the contact in theinput. In this example, contact 720 by finger 202 moves up in contentregion 712 (as shown in FIG. 7F) and content region 712 is scrolled upaccordingly (as shown in FIG. 7G).

FIGS. 7A and 7H illustrate an example of detecting an input (e.g., a tapinput) by a stylus contact (e.g., contact 722 by stylus 203) in thefirst control region (e.g., first control region 714) on an edit modeaffordance (e.g., edit mode affordance 714-d) and displaying the secondcontrol region (e.g., second control region 716, FIG. 7H). In someembodiments, in response to detecting a tap input by a stylus contact(e.g., contact 722 by stylus 203) on edit mode affordance 714-d, userinterface 710 changes from a viewing mode (e.g., in FIG. 7A) to anediting mode (e.g., in FIG. 7H), where the editing mode is distinct fromthe viewing mode. In some embodiments, the editing mode, as shown inFIG. 7H, is configured to enable drawing on content region 712 by astylus (e.g., stylus 203).

FIGS. 7A and 7I illustrate an example of detecting an input (e.g., a tapinput) by a non-stylus contact (e.g., contact 724 by finger 202) in thefirst control region (e.g., first control region 714) on an edit modeaffordance (e.g., edit mode affordance 714-d) and displaying the secondcontrol region (e.g., second control region 716, FIG. 7I). In someembodiments, in response to detecting a tap input by a non-styluscontact (e.g., contact 724 by finger 202) on edit mode affordance 714-d,user interface 710 changes from a viewing mode (e.g., in FIG. 7A) to anediting mode (e.g., in FIG. 7I), where the editing mode is distinct fromthe viewing mode. In some embodiments, the editing mode, as shown inFIG. 7I, is configured to enable drawing on content region 712 by astylus (e.g., stylus 203), but non-stylus contacts in content region 712do not create marks unless a draw affordance (e.g., draw affordance716-a) is selected, as discussed below with respect to FIGS. 7J-7K.

FIGS. 7J-7K illustrate an example of detecting an input that includesmovement across the touch-sensitive display (e.g., touch screen 112) bya non-stylus contact (e.g., contact 726 by finger 202) in the contentregion (e.g., content region 712) when a drawing tool is not selected.In this example, since a drawing tool is not selected (e.g., drawaffordance 716-a is not selected), non-stylus contacts in content region712 do not create marks. In some embodiments, non-stylus contacts incontent region 712 create marks when a drawing tool is selected, asdiscussed below with respect to FIGS. 7L-7M. In some embodiments, asshown in FIG. 7K, a navigation operation is performed in accordance withmovement of the non-stylus contact (e.g., contact 726 by finger 202). Inthis example, contact 726 by finger 202 moves up in content region 712(as shown in FIG. 7J) and content region 712 is scrolled up accordingly(as shown in FIG. 7K).

FIGS. 7L-7M illustrate an example of detecting an input that includesmovement across the touch-sensitive display (e.g., touch screen 112) bya non-stylus contact (e.g., contact 728 by finger 202) in the contentregion (e.g., content region 712) when a drawing tool is selected. Inthis example, since a drawing tool is selected (e.g., draw affordance716-a is selected), a mark (e.g., mark 729) is displayed in accordancewith movement of contact 728 by finger 202. In some embodiments, whendraw affordance 716-a is selected, drawing is enabled on the contentregion by subsequent inputs, regardless of whether the subsequent inputsare made by a stylus contact or a non-stylus contact.

FIGS. 7N-7O illustrate an example of detecting an input that includesmovement across the touch-sensitive display (e.g., touch screen 112) bya stylus contact (e.g., contact 730 by stylus 203) in the content region(e.g., content region 712) when a drawing tool is selected. In someembodiments, while in editing mode (e.g., when second control region 716is displayed), stylus inputs draw marks regardless of whether a drawingtool is selected. For example, in FIGS. 7C-7D, a drawing tool is notselected (e.g., draw affordance 716-a is not selected) and a mark (e.g.,mark 719) is displayed in accordance with movement of contact 718 bystylus 203. In this example, in FIGS. 7N-7O, a drawing tool is selected(e.g., draw affordance 716-a is selected) and a mark (e.g., mark 731) isdisplayed in accordance with movement of contact 730 by stylus 203. Insome embodiments, when movement of the stylus contact is across text,the mark drawn in accordance with movement of the contact ishighlighting on the text, as discussed below with respect to FIGS.7P-7Q. In the example of FIGS. 7N-7O, movement of the stylus contact(e.g., contact 730 by stylus 203) is not across text and the mark (e.g.,mark 731) is a line drawn in accordance with movement of the styluscontact.

FIGS. 7P-7Q illustrate an example of detecting an input that includesmovement across the touch-sensitive display (e.g., touch screen 112) bya stylus contact (e.g., contact 732 by stylus 203) in the content region(e.g., content region 712) when movement of the stylus contact is acrosstext. In this example, since movement of contact 732 by stylus 203 isacross text (e.g., across a number of multiple characters), the markdrawn in accordance with movement of the stylus contact is highlightingon the text (e.g., mark 733 is highlighting the text “The quick brownfox”).

FIG. 7R illustrates an example of detecting an input (e.g., a tap input)in the first control region (e.g., first control region 714) on the editmode affordance (e.g., edit mode affordance 714-d). In some embodiments,in response to detecting a tap input on edit mode affordance 714-d afterediting has occurred, user interface 710 changes from the editing mode(e.g., in FIG. 7Q) to the viewing mode (e.g., in FIG. 7R) and edits madewhile in the editing mode are saved (e.g., mark 731 and mark 733 aresaved). In some embodiments, when user interface 710 changes to theviewing mode (e.g., in FIG. 7R), second control region 716 (e.g., fromFIG. 7Q) is no longer displayed. Although in FIG. 7R, the tap input onedit mode affordance 714-d is shown as contact 734 by stylus 203, anon-stylus contact (e.g., by finger 202) on edit mode affordance 714-dwould have the same result.

FIGS. 8A-8D are flow diagrams illustrating a method 800 of viewing andediting documents with stylus and finger inputs in accordance with someembodiments. The method 800 is performed at an electronic device (e.g.,device 300, FIG. 3, or portable multifunction device 100, FIG. 1A) witha display and a touch-sensitive surface. In some embodiments, thedisplay is a touch screen display and the touch-sensitive surface is onor integrated with the display (also called simply a touch-sensitivedisplay). In some embodiments, the display is separate from thetouch-sensitive surface. In some embodiments, the device includes one ormore sensors to detect signals from a stylus associated with the device.Some operations in method 800 are, optionally, combined and/or the orderof some operations is, optionally, changed.

As described below, the method 800 provides an intuitive way to view andedit documents with stylus and finger inputs, allowing simultaneousannotation with stylus inputs and navigation with finger inputs withouthaving to activate a mode-change affordance. The method reduces thenumber, extent, and/or nature of the inputs from a user when using astylus and non-stylus to interact with an electronic device, therebycreating a more efficient human-machine interface. For battery-operatedelectronic devices, enabling a user to enter inputs faster and moreefficiently conserves power and increases the time between batterycharges.

The device displays (802) a user interface in a viewing mode (e.g., aread-only mode or other mode that does not permit markup or editing ofthe content) on the touch-sensitive display, the user interfaceincluding a content region and a first control region. FIG. 7A, forexample, shows user interface 710 in a viewing mode on touch screen 112,user interface 710 including content region 712 and first control region714. In some embodiments, the first control region includes controls forediting the content. In some embodiments, the first control regionincludes controls for navigating through the content. In FIG. 7A, forexample, first control region 714 includes menu affordance 714-a,deletion affordance 714-b, revert affordance 714-c, edit mode affordance714-d, and sharing affordance 714-e, as described above with respect toFIG. 7A.

The device, while displaying the user interface in the viewing mode(e.g., in FIG. 7A), detects (804) an input by a first contact on thetouch-sensitive display (e.g., touch screen 112). FIG. 7C, for example,shows detecting an input by a stylus contact (e.g., contact 718 bystylus 203) in the content region (e.g., content region 712). As anotherexample, FIG. 7F shows detecting an input by a non-stylus contact (e.g.,contact 720 by finger 202) in the content region (e.g., content region712). As yet another example, FIG. 7H shows detecting an input by astylus contact (e.g., contact 722 by stylus 203) in the first controlregion (e.g., first control region 714). As yet another example, FIG. 7Ishows detecting an input by a non-stylus contact (e.g., contact 724 byfinger 202) in the first control region (e.g., first control region714).

The device, in response to detecting the input (806), performs a numberof operations. In response to detecting the input, in accordance with adetermination that the first contact is a stylus contact in the contentregion (e.g., an input that includes movement across the touch-sensitivedisplay, such as contact 718 by stylus 203 in FIG. 7C), the devicechanges from the viewing mode (e.g., in FIG. 7A) to an editing mode(e.g., in FIG. 7C), distinct from the viewing mode, that is configuredto enable drawing on the content region in the user interface, and thedevice displays, in the content region, a mark drawn in accordance withmovement of the first contact in the input (e.g., a mark based on a pathof the input on the touch-sensitive display, such as mark 719 in FIG.7D). Changing from the viewing mode to the editing mode without havingto activate a mode-changing affordance enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byreducing the number, extent, and/or nature of the inputs from the userand by helping the user to provide proper inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In response to detecting the input, in accordance with a determinationthat the first contact is a non-stylus contact (e.g., a finger contact)in the content region (e.g., an input that includes movement across thetouch-sensitive display, such as contact 720 by finger 202 in FIG. 7F),the device remains in the viewing mode (e.g., forgoes changing from theviewing mode to the editing mode), and the device performs a navigationoperation in the content region in accordance with movement of the firstcontact in the input (e.g., performs a scrolling operation or othernavigation action in accordance with the input, as shown in FIGS. 7F-7G)without displaying the mark that corresponds to the first contact in thecontent region (e.g., forgoes displaying the mark). Allowingsimultaneous annotation with stylus inputs and navigation withnon-stylus inputs without having to activate a mode-change affordanceenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the number, extent, and/ornature of the inputs from the user and by helping the user to provideproper inputs and reducing user mistakes when operating/interacting withthe device) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In response to detecting the input, in accordance with a determinationthat the first contact is a stylus contact in the first control region(e.g., a tap input, such as contact 722 by stylus 203 in FIG. 7H), thedevice performs a control operation. In some embodiments, the controloperation includes displaying a second control region (e.g., an editingtoolbar) that includes a plurality of controls for the editing mode inresponse to detecting a tap input on an edit mode affordance (e.g., editmode affordance 714-d), as shown in FIG. 7H. In some embodiments, thecontrol operation includes deleting a document in response to detectinga tap input on a deletion affordance (e.g., deletion affordance 714-b),sharing a document in response to detecting a tap input on a sharingaffordance (e.g., sharing affordance 714-e), displaying a menu foropening a document in response to detecting a tap input on a menuaffordance (e.g., menu affordance 714-a), and undoing changes inresponse to detecting a tap input on a revert affordance (e.g., revertaffordance 714-c). Optionally, when the device performs the controloperation, the device remains in the viewing mode. In response todetecting the input, in accordance with a determination that the firstcontact is a non-stylus contact in the first control region (e.g., a tapinput, such as contact 724 by finger 202 in FIG. 7I), the deviceperforms the control operation (and optionally, remains in the viewingmode). In FIG. 7I, the control operation includes displaying a secondcontrol region (e.g., second control region 716) that includes aplurality of controls for the editing mode in response to detecting atap input (e.g., contact 724 by finger 202) on an edit mode affordance(e.g., edit mode affordance 714-d). Allowing both stylus inputs andnon-stylus inputs to select affordances in the first control regionenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the number, extent, and/ornature of the inputs from the user and by helping the user to provideproper inputs and reducing user mistakes when operating/interacting withthe device) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, in accordance with a determination that the firstcontact is the stylus contact in the content region, the mark drawn inaccordance with movement of the first contact in the input is displayed(808) without performing the navigation operation. For example, in FIGS.7C-7D, mark 719 is drawn in accordance with movement of contact 718 bystylus 203 without performing a navigation operation.

In some embodiments, in accordance with a determination that the firstcontact is the stylus contact in the content region (e.g., an input thatincludes movement across the touch-sensitive display) (810): inaccordance with a determination that movement of the first contact inthe input is across text (e.g., across a number of multiple characters,such as movement of contact 732 by stylus 203 in FIG. 7P), the markdrawn in accordance with movement of the first contact is highlightingon the text (e.g., mark 733 in FIG. 7Q); and, in accordance with adetermination that movement of the first contact in the input is notacross text (e.g., such as movement of contact 730 by stylus 203 in FIG.7N), the mark drawn in accordance with movement of the first contact inthe input is a line drawn in accordance with movement of the firstcontact in the input (e.g., mark 731 in FIG. 7O). Allowing a stylusinput to both highlight text and annotate a document without having toactivate an affordance to change drawing tools enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by reducing the number, extent, and/or nature of the inputs from theuser and by helping the user to provide proper inputs and reducing usermistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some embodiments, in accordance with a determination that the firstcontact is the stylus contact in the content region (e.g., contact 718by stylus 203 in content region 712, FIG. 7B), the device displays (812)a second control region (e.g., second control region 716), distinct fromthe first control region (e.g., first control region 714), that includesa plurality of controls for the editing mode. In some embodiments, thesecond control region (e.g., second control region 716, FIG. 7B)includes one or more tools, such as a drawing tool (e.g., drawaffordance 716-a, FIG. 7B) to enable drawing on the content region(where both stylus contacts and non-stylus contacts are enabled to makemarks in the content region), a zoom tool (e.g., zoom affordance 716-b,FIG. 7B) to change the magnification of a selected portion of thedocument, a text tool (e.g., text affordance 716-c, FIG. 7B) to typetext in a text box, a signature tool (e.g., signature affordance 716-d,FIG. 7B) to insert a signature into a PDF document, a color tool (e.g.,color affordance 716-e, FIG. 7B) to change the color of marks drawn inthe content region, a line thickness tool (e.g., thickness affordance716-f, FIG. 7B) to change the thickness of the marks drawn in thecontent region, and a font tool (e.g., font affordance 716-g, FIG. 7B)to change the font type, font size, and/or font alignment of text in thedocument. In some embodiments, in accordance with a determination thatthe first contact is the non-stylus contact in the content region (e.g.,contact 720 by finger 202 in content region 712, FIG. 7E), the deviceforgoes displaying the second control region, as shown in FIG. 7E.

In some embodiments, in accordance with a determination that the firstcontact is the stylus contact in the content region, displaying thesecond control region includes (814) displaying an animation of thesecond control region appearing on the touch-sensitive display beginningat a time of initial contact of the stylus contact in the contentregion. In FIG. 7B, for example, second control region 716 is displayedby an animation of second control region 716 appearing on touch screen112 beginning at a time of initial contact of stylus 203 in contentregion 712. Fading in the second control region leaves the contentregion stationary and the stylus contact does not cause changes in thecontent region other than making marks. This enhances the operability ofthe device and makes the user-device interface more user-friendly andefficient (e.g., by not distracting the user with a sudden entry intothe editing mode, thus helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, in accordance with a determination that the firstcontact is the non-stylus contact in the first control region (e.g., atap input) on an edit mode affordance, the device displays (816) thesecond control region. For example, FIG. 7I shows displaying secondcontrol region 716 when the non-stylus contact in the first controlregion (e.g., contact 724 by finger 202 in first control region 714) ison an edit mode affordance (e.g., edit mode affordance 714-d).

In some embodiments, while displaying the second control region, thedevice detects (818) a third input by a third contact on thetouch-sensitive display; and, in response to detecting the third input:in accordance with a determination that the third contact is a contactin the second control region (e.g., a tap input) on a draw affordance(e.g., selecting a drawing tool), enabling drawing on the content regionin the user interface by subsequent inputs, regardless of whether thesubsequent inputs are made by a stylus contact or a non-stylus contact.For example, in FIG. 7L, draw affordance 716-a has been selected, sodrawing is enabled on content region 712 by subsequent inputs,regardless of whether the subsequent inputs are made by a stylus contact(e.g., contact 730 by stylus 203 in FIGS. 7N-7O) or a non-stylus contact(e.g., contact 728 by finger 202 in FIGS. 7L-7M).

In some embodiments, non-stylus contacts in the content region do notcreate (820) marks unless the draw affordance is selected. For example,in FIGS. 7J-7K, although second control region 716 is displayed, drawaffordance 716-a has not been selected, so the non-stylus contact in thecontent region (e.g., contact 726 by finger 202 in content region 712)does not create a mark.

In some embodiments, while displaying the user interface in the editingmode, the device detects (822) a second input by a second contact on thetouch-sensitive display. The device, in response to detecting the secondinput, performs a number of operations. In response to detecting thesecond input, in accordance with a determination that the second contactis a second stylus contact in the content region (e.g., an input thatincludes movement across the touch-sensitive display): the devicedisplays, in the content region, a second mark drawn in accordance withmovement of the second contact in the second input (e.g., a mark basedon a path of the second input on the touch-sensitive display). In someembodiments, while displaying the user interface in the editing mode,stylus inputs draw marks without regard to whether a drawing tool isselected. FIGS. 7C-7D, for example, show mark 719 drawn in accordancewith movement of contact 718 by stylus 203 where a drawing tool is notselected (e.g., draw affordance 716-a is not selected). FIGS. 7N-7O, forexample, show mark 731 drawn in accordance with movement of contact 730by stylus 203 where a drawing tool is selected (e.g., draw affordance716-a is selected).

In response to detecting the second input, in accordance with adetermination that the second contact is a second non-stylus contact inthe content region (e.g., a finger contact of an input that includesmovement across the touch-sensitive display): in accordance with adetermination that a drawing tool is selected (e.g., from the secondcontrol region), the device displays, in the content region, the secondmark drawn in accordance with movement of the second contact in thesecond input. For example, in FIGS. 7L-7M, mark 729 is drawn inaccordance with movement of contact 728 by finger 202 when drawaffordance 716-a is selected. In some embodiments, when the drawing toolis selected, a stylus input draws and a finger input draws. In responseto detecting the second input, in accordance with a determination thatthe second contact is a second non-stylus contact in the content region(e.g., a finger contact of an input that includes movement across thetouch-sensitive display): in accordance with a determination that thedrawing tool is not selected, the device forgoes displaying the secondmark and optionally, performs a second navigation operation in thecontent region in accordance with movement of the second contact in thesecond input (e.g., performing a scrolling operation or other navigationaction in accordance with the second input). For example, in FIGS.7J-7K, contact 726 by finger 202 is detected in content region 712, butdraw affordance 716-a is not selected, so no mark is displayed and anavigation operation in accordance with movement of contact 726 byfinger 202 is performed. Allowing a non-stylus input to both annotate adocument (e.g., when draw affordance 716-a is selected) and navigate inthe document (e.g., when draw affordance 716-a is not selected) enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to provide proper inputs andreducing user mistakes when operating/interacting with the device)which, additionally, reduces power usage and improves battery life ofthe device by enabling the user to use the device more quickly andefficiently.

In some embodiments, while displaying the user interface in the editingmode, the device detects (824) a fourth input by a fourth contact on thetouch-sensitive display; and, in response to detecting the fourth input:in accordance with a determination that the fourth contact (e.g., styluscontact or non-stylus contact) is in the first control region (e.g., atap input) on the edit mode affordance: the device changes from theediting mode to the viewing mode; and the device saves edits made whilein the editing mode. FIG. 7R, for example, shows a contact (e.g.,contact 734) in first control region 714 on edit mode affordance 714-d,and in response, the device changes from the editing mode (e.g., in FIG.7Q, where second control region 716 is displayed) to the viewing mode(e.g., in FIG. 7R) and edits made while in the editing mode are saved(e.g., mark 731 and mark 733 are saved and displayed in the viewing modein FIG. 7R).

In some embodiments, the device displays (826) an object with aselection handle in the content region in the editing mode (e.g., a textbox added with text affordance 716-c, FIG. 7B). While displaying theobject with the selection handle in the content region in the editingmode, the device detects a fifth input by a fifth contact on thetouch-sensitive display at a location corresponding to the selectionhandle. In response to detecting the fifth input: in accordance with adetermination that the fifth contact is the non-stylus contact in thecontent region (e.g., a non-stylus input that includes movement acrossthe touch-sensitive display), the devices moves the selection handle inaccordance with movement of the fifth contact in the fifth input (e.g.,to move and/or enlarge text boxes in the content region). In someembodiments, non-stylus contacts (e.g., finger contacts) operateselection handles, but stylus contacts do not operate selection handles.Allowing stylus inputs and non-stylus inputs to perform separatefunctions without having to activate a function-change affordanceenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by reducing the number, extent, and/ornature of the inputs from the user and by helping the user to provideproper inputs and reducing user mistakes when operating/interacting withthe device) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some embodiments, in response to detecting the fifth input: inaccordance with a determination that the fifth contact is the styluscontact in the content region (e.g., a stylus input that includesmovement across the touch-sensitive display): the device forgoes (828)moving the selection handle, and the device displays, in the contentregion, a third mark drawn in accordance with movement of the fifthcontact in the fifth input.

It should be understood that the particular order in which theoperations in FIGS. 8A-8D have been described is merely exemplary and isnot intended to indicate that the described order is the only order inwhich the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein.

In accordance with some embodiments, FIG. 9 shows a functional blockdiagram of an electronic device 900 configured in accordance with theprinciples of the various described embodiments. The functional blocksof the device are, optionally, implemented by hardware, software,firmware, or a combination thereof to carry out the principles of thevarious described embodiments. It is understood by persons of skill inthe art that the functional blocks described in FIG. 9 are, optionally,combined or separated into sub-blocks to implement the principles of thevarious described embodiments. Therefore, the description hereinoptionally supports any possible combination or separation or furtherdefinition of the functional blocks described herein.

As shown in FIG. 9, an electronic device 900 includes a touch-sensitivedisplay unit 902 configured to display a user interface and receive userinputs (including user inputs by stylus and non-stylus contacts, one ormore sensor units 906 configured to detect signals from a stylusassociated with the device; and a processing unit 908 coupled with thetouch-sensitive display unit 902 and the one or more sensor units 906.In some embodiments, the processing unit 908 includes a display enablingunit 910, a detecting unit 912, a mode unit 914, a navigation unit 916,and a control unit 918.

The processing unit 908 is configured to: enable display of a userinterface in a viewing mode on the touch-sensitive display unit 902(e.g., with the display enabling unit 910), the user interface includinga content region and a first control region; while enabling displayingof the user interface in the viewing mode, detect an input by a firstcontact on the touch-sensitive display unit 902 (e.g., with thedetecting unit 912); and, in response to detecting the input: inaccordance with a determination that the first contact is a styluscontact in the content region: change from the viewing mode to anediting mode (e.g., with the mode unit 914), distinct from the viewingmode, that is configured to enable drawing on the content region in theuser interface; and enable display of, in the content region, a markdrawn in accordance with movement of the first contact in the input(e.g., with the display enabling unit 910); in accordance with adetermination that the first contact is a non-stylus contact in thecontent region: remain in the viewing mode (e.g., with the mode unit914); and perform a navigation operation (e.g., with the navigation unit916) in the content region in accordance with movement of the firstcontact in the input without enabling display of the mark thatcorresponds to the first contact in the content region; in accordancewith a determination that the first contact is a stylus contact in thefirst control region, perform a control operation (e.g., with thecontrol unit 918); and in accordance with a determination that the firstcontact is a non-stylus contact in the first control region, perform thecontrol operation (e.g., with the control unit 918).

In some embodiments, in accordance with a determination that the firstcontact is the stylus contact in the content region, the mark drawn inaccordance with movement of the first contact in the input is displayedwithout performing the navigation operation.

In some embodiments, the processing unit 908 is configured to: inaccordance with a determination that the first contact is the styluscontact in the content region: enable display of a second controlregion, distinct from the first control region, that includes aplurality of controls for the editing mode (e.g., with the displayenabling unit 910); and, in accordance with a determination that thefirst contact is the non-stylus contact in the content region: forgoenabling display of the second control region (e.g., with the displayenabling unit 910).

In some embodiments, in accordance with a determination that the firstcontact is the stylus contact in the content region, enabling display ofthe second control region includes enabling display of an animation ofthe second control region appearing on the touch-sensitive display unit902 beginning at a time of initial contact of the stylus contact in thecontent region.

In some embodiments, the processing unit 908 is configured to: inaccordance with a determination that the first contact is the non-styluscontact in the first control region on an edit mode affordance, enabledisplay of the second control region (e.g., with the display enablingunit 910).

In some embodiments, the processing unit 908 is configured to: whileenabling display of the user interface in the editing mode, detect asecond input by a second contact on the touch-sensitive display unit 902(e.g., with the detecting unit 912); and, in response to detecting thesecond input: in accordance with a determination that the second contactis a second stylus contact in the content region: enable display of, inthe content region, a second mark drawn in accordance with movement ofthe second contact in the second input (e.g., with the display enablingunit 910); in accordance with a determination that the second contact isa second non-stylus contact in the content region: in accordance with adetermination that a drawing tool is selected, enable display of, in thecontent region, the second mark drawn in accordance with movement of thesecond contact in the second input (e.g., with the display enabling unit910); and in accordance with a determination that the drawing tool isnot selected, forgo enabling display of the second mark (e.g., with thedisplay enabling unit 910).

In some embodiments, the processing unit 908 is configured to: whileenabling display of the second control region, detect a third input by athird contact on the touch-sensitive display unit 902 (e.g., with thedetecting unit 912); and, in response to detecting the third input: inaccordance with a determination that the third contact is a contact inthe second control region on a draw affordance, enable drawing on thecontent region in the user interface by subsequent inputs, regardless ofwhether the subsequent inputs are made by a stylus contact or anon-stylus contact (e.g., with the control unit 918).

In some embodiments, non-stylus contacts in the content region do notcreate marks unless the draw affordance is selected.

In some embodiments, in accordance with a determination that the firstcontact is the stylus contact in the content region: in accordance witha determination that movement of the first contact in the input isacross text, the mark drawn in accordance with movement of the firstcontact is highlighting on the text; and in accordance with adetermination that movement of the first contact in the input is notacross text, the mark drawn in accordance with movement of the firstcontact in the input is a line drawn in accordance with movement of thefirst contact in the input.

In some embodiments, the processing unit 908 is configured to: whileenabling display of the user interface in the editing mode, detect afourth input by a fourth contact on the touch-sensitive display unit 902(e.g., with the detecting unit 912); and, in response to detecting thefourth input: in accordance with a determination that the fourth contactis in the first control region on the edit mode affordance: change fromthe editing mode to the viewing mode (e.g., with the mode unit 914); andsave edits made while in the editing mode (e.g., with the control unit918).

In some embodiments, the processing unit 908 is configured to: enabledisplay of an object with a selection handle in the content region inthe editing mode (e.g., with the display enabling unit 910); whileenabling display of the object with the selection handle in the contentregion in the editing mode, detect a fifth input by a fifth contact onthe touch-sensitive display unit 902 at a location corresponding to theselection handle (e.g., with the detecting unit 912); and, in responseto detecting the fifth input: in accordance with a determination thatthe fifth contact is the non-stylus contact in the content region, movethe selection handle in accordance with movement of the fifth contact inthe fifth input (e.g., with the control unit 918).

In some embodiments, the processing unit 908 is configured to: inresponse to detecting the fifth input: in accordance with adetermination that the fifth contact is the stylus contact in thecontent region: forgo moving the selection handle (e.g., with thecontrol unit 918); and enable display of, in the content region, a thirdmark drawn in accordance with movement of the fifth contact in the fifthinput (e.g., with the display enabling unit 910).

The operations in the information processing methods described aboveare, optionally implemented by running one or more functional modules ininformation processing apparatus such as general purpose processors(e.g., as described above with respect to FIGS. 1A and 3) or applicationspecific chips.

The operations described above with reference to FIGS. 8A-8D are,optionally, implemented by components depicted in FIGS. 1A-1B or FIG. 9.For example, display operation 802, detection operation 804, andresponse operation 806 are, optionally, implemented by event sorter 170,event recognizer 180, and event handler 190. Event monitor 171 in eventsorter 170 detects a contact (or near contact) on touch-sensitivedisplay 112, and event dispatcher module 174 delivers the eventinformation to application 136-1. A respective event recognizer 180 ofapplication 136-1 compares the event information to respective eventdefinitions 186, and determines whether a first contact (or nearcontact) at a first location on the touch-sensitive surface (or whetherrotation of the device) corresponds to a predefined event or sub-event,such as selection of an object on a user interface, or rotation of thedevice from one orientation to another. When a respective predefinedevent or sub-event is detected, event recognizer 180 activates an eventhandler 190 associated with the detection of the event or sub-event.Event handler 190 optionally uses or calls data updater 176 or objectupdater 177 to update the application internal state 192. In someembodiments, event handler 190 accesses a respective GUI updater 178 toupdate what is displayed by the application. Similarly, it would beclear to a person having ordinary skill in the art how other processescan be implemented based on the components depicted in FIGS. 1A-1B.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A non-transitory computer readable storage mediumstoring one or more programs, the one or more programs comprisinginstructions which, when executed by an electronic device with atouch-sensitive display and one or more sensors to detect signals from astylus associated with the electronic device, cause the electronicdevice to: display a user interface in a viewing mode on thetouch-sensitive display, the user interface including a content regionand a first control region; while displaying the user interface in theviewing mode, detect an input by a first contact on the touch-sensitivedisplay; and, in response to detecting the input: in accordance with adetermination that the first contact is a stylus contact in the contentregion, display, in the content region, a mark drawn in accordance withmovement of the first contact in the input: in accordance with adetermination that the first contact is a non-stylus contact in thecontent region, perform a navigation operation in the content region inaccordance with movement of the first contact in the input withoutdisplaying the mark that corresponds to the first contact in the contentregion; in accordance with a determination that the first contact is astylus contact in the first control region, perform a control operation;and in accordance with a determination that the first contact is anon-stylus contact in the first control region, perform the controloperation.
 2. The storage medium of claim 1, wherein in accordance witha determination that the first contact is the stylus contact in thecontent region, the mark drawn in accordance with movement of the firstcontact in the input is displayed without performing the navigationoperation.
 3. The storage medium of claim 1, wherein the one or moreprograms include instructions which, when executed by the electronicdevice, cause the electronic device to: in accordance with adetermination that the first contact is the stylus contact in thecontent region: display a second control region, distinct from the firstcontrol region, that includes a plurality of controls for changing avisual appearance of marks made in the content region; and, inaccordance with a determination that the first contact is the non-styluscontact in the content region: forgo displaying the second controlregion.
 4. The storage medium of claim 3, wherein the one or moreprograms include instructions which, when executed by the electronicdevice, cause the electronic device to: in accordance with adetermination that the first contact is the stylus contact in thecontent region, display an animation of the second control regionappearing on the touch-sensitive display beginning at a time of initialcontact of the stylus contact in the content region.
 5. The storagemedium of claim 3, wherein the one or more programs include instructionswhich, when executed by the electronic device, cause the electronicdevice to: in accordance with a determination that the first contact isthe non-stylus contact in the first control region on an edit modeaffordance, display the second control region.
 6. The storage medium ofclaim 3, wherein the one or more programs include instructions which,when executed by the electronic device, cause the electronic device to:while displaying the second control region, detect a third input by athird contact on the touch-sensitive display; and, in response todetecting the third input: in accordance with a determination that thethird contact is a contact in the second control region on a drawaffordance, enable drawing on the content region in the user interfaceby subsequent inputs, regardless of whether the subsequent inputs aremade by a stylus contact or a non-stylus contact.
 7. The storage mediumof claim 6, wherein non-stylus contacts in the content region do notcreate marks unless the draw affordance is selected.
 8. The storagemedium of claim 1, wherein the one or more programs include instructionswhich, when executed by the electronic device, cause the electronicdevice to: while displaying the user interface, detect a second input bya second contact on the touch-sensitive display; and, in response todetecting the second input: in accordance with a determination that thesecond contact is a second stylus contact in the content region:display, in the content region, a second mark drawn in accordance withmovement of the second contact in the second input; in accordance with adetermination that the second contact is a second non-stylus contact inthe content region: in accordance with a determination that a drawingtool is selected, display, in the content region, the second mark drawnin accordance with movement of the second contact in the second input;and in accordance with a determination that the drawing tool is notselected, forgo displaying the second mark.
 9. The storage medium ofclaim 1, wherein: in accordance with a determination that the firstcontact is the stylus contact in the content region: in accordance witha determination that movement of the first contact in the input isacross text, the mark drawn in accordance with movement of the firstcontact is highlighting on the text; and in accordance with adetermination that movement of the first contact in the input is notacross text, the mark drawn in accordance with movement of the firstcontact in the input is a line drawn in accordance with movement of thefirst contact in the input.
 10. The storage medium of claim 1, whereinthe one or more programs include instructions which, when executed bythe electronic device, cause the electronic device to: while displayingthe user interface, wherein the user interface is in an editing mode,detect a fourth input by a fourth contact on the touch-sensitivedisplay; and, in response to detecting the fourth input: in accordancewith a determination that the fourth contact is on a mode affordance inthe first control region: change to a viewing mode that does not permitediting of content in the content region; and save edits previouslymade.
 11. The storage medium of claim 1, wherein the one or moreprograms include instructions which, when executed by the electronicdevice, cause the electronic device to: display an object with aselection handle in the content region; while displaying the object withthe selection handle in the content region, detect a fifth input by afifth contact on the touch-sensitive display at a location correspondingto the selection handle; and, in response to detecting the fifth input:in accordance with a determination that the fifth contact is thenon-stylus contact in the content region, move the selection handle inaccordance with movement of the fifth contact in the fifth input. 12.The storage medium of claim 11, wherein the one or more programs includeinstructions which, when executed by the electronic device, cause theelectronic device to: in response to detecting the fifth input: inaccordance with a determination that the fifth contact is the styluscontact in the content region: forgo moving the selection handle; anddisplay, in the content region, a third mark drawn in accordance withmovement of the fifth contact in the fifth input.
 13. An electronicdevice, comprising: a touch-sensitive display; one or more sensors todetect signals from a stylus associated with the device; one or moreprocessors; memory; and one or more programs, wherein the one or moreprograms are stored in the memory and configured to be executed by theone or more processors, the one or more programs including instructionsfor: displaying a user interface in a viewing mode on thetouch-sensitive display, the user interface including a content regionand a first control region; while displaying the user interface in theviewing mode, detecting an input by a first contact on thetouch-sensitive display; and, in response to detecting the input: inaccordance with a determination that the first contact is a styluscontact in the content region, displaying, in the content region, a markdrawn in accordance with movement of the first contact in the input: inaccordance with a determination that the first contact is a non-styluscontact in the content region: performing a navigation operation in thecontent region in accordance with movement of the first contact in theinput without displaying the mark that corresponds to the first contactin the content region; in accordance with a determination that the firstcontact is a stylus contact in the first control region, performing acontrol operation; and in accordance with a determination that the firstcontact is a non-stylus contact in the first control region, performingthe control operation.
 14. The electronic device of claim 13, wherein inaccordance with a determination that the first contact is the styluscontact in the content region, the mark drawn in accordance withmovement of the first contact in the input is displayed withoutperforming the navigation operation.
 15. The electronic device of claim13, wherein the one or more programs include instructions for: inaccordance with a determination that the first contact is the styluscontact in the content region: displaying a second control region,distinct from the first control region, that includes a plurality ofcontrols for changing a visual appearance of marks made in the contentregion; and, in accordance with a determination that the first contactis the non-stylus contact in the content region: forgoing displaying thesecond control region.
 16. The electronic device of claim 15, whereinthe one or more programs include instructions for: in accordance with adetermination that the first contact is the stylus contact in thecontent region, displaying an animation of the second control regionappearing on the touch-sensitive display beginning at a time of initialcontact of the stylus contact in the content region.
 17. The electronicdevice of claim 15, wherein the one or more programs includeinstructions for: in accordance with a determination that the firstcontact is the non-stylus contact in the first control region on an editmode affordance, displaying the second control region.
 18. Theelectronic device of claim 15, wherein the one or more programs includeinstructions for: while displaying the second control region, detectinga third input by a third contact on the touch-sensitive display; and, inresponse to detecting the third input: in accordance with adetermination that the third contact is a contact in the second controlregion on a draw affordance, enabling drawing on the content region inthe user interface by subsequent inputs, regardless of whether thesubsequent inputs are made by a stylus contact or a non-stylus contact.19. The electronic device of claim 18, wherein non-stylus contacts inthe content region do not create marks unless the draw affordance isselected.
 20. A method, comprising: at an electronic device with atouch-sensitive display, the device including one or more sensors todetect signals from a stylus associated with the device: displaying auser interface in a viewing mode on the touch-sensitive display, theuser interface including a content region and a first control region;while displaying the user interface in the viewing mode, detecting aninput by a first contact on the touch-sensitive display; and, inresponse to detecting the input: in accordance with a determination thatthe first contact is a stylus contact in the content region, displaying,in the content region, a mark drawn in accordance with movement of thefirst contact in the input: in accordance with a determination that thefirst contact is a non-stylus contact in the content region, performinga navigation operation in the content region in accordance with movementof the first contact in the input without displaying the mark thatcorresponds to the first contact in the content region; in accordancewith a determination that the first contact is a stylus contact in thefirst control region, performing a control operation; and in accordancewith a determination that the first contact is a non-stylus contact inthe first control region, performing the control operation.
 21. Themethod of claim 20, wherein in accordance with a determination that thefirst contact is the stylus contact in the content region, the markdrawn in accordance with movement of the first contact in the input isdisplayed without performing the navigation operation.
 22. The method ofclaim 20, including: in accordance with a determination that the firstcontact is the stylus contact in the content region: displaying a secondcontrol region, distinct from the first control region, that includes aplurality of controls for changing a visual appearance of marks made inthe content region; and, in accordance with a determination that thefirst contact is the non-stylus contact in the content region: forgoingdisplaying the second control region.
 23. The method of claim 22,including: in accordance with a determination that the first contact isthe stylus contact in the content region, displaying an animation of thesecond control region appearing on the touch-sensitive display beginningat a time of initial contact of the stylus contact in the contentregion.
 24. The method of claim 22, including: in accordance with adetermination that the first contact is the non-stylus contact in thefirst control region on an edit mode affordance, displaying the secondcontrol region.
 25. The method of claim 22, including: while displayingthe second control region, detecting a third input by a third contact onthe touch-sensitive display; and, in response to detecting the thirdinput: in accordance with a determination that the third contact is acontact in the second control region on a draw affordance, enablingdrawing on the content region in the user interface by subsequentinputs, regardless of whether the subsequent inputs are made by a styluscontact or a non-stylus contact.